Summary

• Adds a Skills as Resources reference implementation at examples/skills-as-resources/, demonstrating the MCP Resources approach to skill delivery using the skill:// URI scheme
• Answers Open Question 12 ("why not just resources?") with a working implementation
• Includes both TypeScript and Python implementations with shared sample skills, mirroring the structure of the skills-as-tools example (Add Skills as Tools reference implementation (Approach 3) #15)

Five resource types

Key design decisions

• Application-controlled: Resources are read by the host/client, not invoked by the model — demonstrates a fundamentally different control model than Skills as Tools
• Static resources for skills, template for documents: Each skill becomes a concrete resource in resources/list; only document fetching uses a ResourceTemplate
• Progressive disclosure via URI hierarchy: skill://index → skill://{name} → skill://{name}/documents → skill://{name}/document/{path}
• SDK difference documented: TypeScript uses RFC 6570 {+path} expansion for natural slashes; Python URL-encodes slashes (SDK auto-decodes)

Attribution

Substantially derived from skills-over-mcp by @keithagroves, with additional patterns from skilljack-mcp by @olaservo. Python implementation and security model are original.

Test plan

• TypeScript: cd examples/skills-as-resources/typescript && npm install && npm run build compiles cleanly
• Python: cd examples/skills-as-resources/python && pip install -e . installs cleanly
• Both discover 2 skills (code-review with 1 document, git-commit-review with 0)
• MCP Inspector: verify resources/list returns all expected resources
• MCP Inspector: verify resources/read on skill://index returns valid JSON
• MCP Inspector: verify resources/read on skill://prompt-xml returns valid XML
• MCP Inspector: verify resources/read on skill://code-review returns SKILL.md content
• MCP Inspector: verify document template returns references/REFERENCE.md content

🦉 Generated with Claude Code